Systems and methods for processing preauthorized automated banking machine-related transactions

ABSTRACT

Embodiments of the disclosure enable a transaction to be preauthorized. A system receives a request for preauthorization of a transaction including a transaction amount and a cardholder identifier, identifies a cardholder account based on the cardholder identifier, determines a transaction timeframe and a machine identifier, and accesses the cardholder account to determine whether to process the transaction in accordance with a nonvisual communication program. On condition that the transaction is to be processed in accordance with the nonvisual communication program, the system generates an instruction to identify a capture time, determine whether the capture time satisfies the transaction timeframe, and dispense the transaction amount of cash in accordance with the nonvisual communication program on condition that the capture time satisfies the transaction timeframe. Aspects of the disclosure provide for preauthorizing the transaction in a secure and user-friendly manner.

FIELD OF THE DISCLOSURE

The subject matter described herein relates generally to informationprocessing and, more specifically, to systems and methods for processingone or more preauthorized automated banking machine-relatedtransactions.

BACKGROUND

Automated banking machines have made great gains as a means to attractfinancial accounts to financial institutions. For example, at least someautomated banking machines have made it easier for cardholders to enterinto at least some financial transactions, such as deposit transactions,cash withdrawal transactions, and check cashing transactions. At leastsome cardholders, however, are deterred from using automated bankingmachines for various reasons. A cardholder who prefers to enter into afinancial transaction using nonvisual communication, for example, mayperceive that using at least some known automated banking machines isrisky, tedious, and/or time-consuming.

SUMMARY

Embodiments of the disclosure enable a computing system to preauthorizeone or more financial transactions. The computing system includes amemory device storing data associated with one or more cardholderaccounts and computer-executable instructions, and a processor. Theprocessor executes the computer-executable instructions to receive arequest for preauthorization of a financial transaction including atransaction amount and a cardholder identifier, identify a cardholderaccount based on the cardholder identifier, determine a transactiontimeframe and a machine identifier associated with the financialtransaction, and access the cardholder account to determine whether toprocess the financial transaction in accordance with a nonvisualcommunication program. On condition that the financial transaction is tobe processed in accordance with the nonvisual communication program, theprocessor is configured to generate an instruction to identify a capturetime associated with the financial transaction, determine whether thecapture time satisfies the transaction timeframe, and dispense thetransaction amount of cash in accordance with the nonvisualcommunication program on condition that the capture time satisfies thetransaction timeframe.

In another aspect, one or more computer storage media embodied withcomputer-executable instructions are provided. The computer storagemedia includes a preauthorization component, a detection component, anda dispenser component. The preauthorization component obtains apreauthorization message associated with a financial transaction, andanalyzes the preauthorization message to identify a transaction amountand a cardholder account associated with the financial transaction. Thedetection component determines that a cardholder associated with thecardholder account is proximate to a cash machine, identifies a capturetime associated with the financial transaction, and determines whetherthe capture time satisfies the transaction timeframe. The dispensercomponent dispenses the transaction amount of cash in accordance with anonvisual communication program.

In yet another aspect, a computer-implemented method is provided forpreauthorizing one or more financial transactions. Thecomputer-implemented method includes identifying a request forpreauthorization of a financial transaction including a transactionamount and a cardholder identifier, determining a transaction timeframeassociated with the financial transaction, identifying a cash machineassociated with the financial transaction, and determining whether toprocess the financial transaction in accordance with a nonvisualcommunication program. On condition that the financial transaction is tobe processed in accordance with the nonvisual communication program, thecomputer-implemented method includes generating a preauthorizationinstruction to dispense the transaction amount of cash in accordancewith the nonvisual communication program upon determining that a capturetime associated with the financial transaction satisfies the transactiontimeframe.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating an example environment forprocessing financial transactions.

FIG. 2 is a block diagram illustrating an example ecosystem forprocessing financial transactions in an environment, such as theenvironment shown in FIG. 1.

FIG. 3 is a block diagram illustrating an example computing system forprocessing preauthorized financial transactions in an ecosystem, such asthe ecosystem shown in FIG. 2.

FIG. 4 is a flowchart of an example method for processing preauthorizedfinancial transactions using a computing system, such as the computingsystem shown in FIG. 3.

FIG. 5 is a block diagram illustrating example components that may beused to process preauthorized financial transactions in an ecosystem,such as the ecosystem shown in FIG. 2.

FIG. 6 is a sequence diagram of an example method for processingpreauthorized financial transactions in an ecosystem, such as theecosystem shown in FIG. 2.

FIG. 7 is a flow diagram of an example dataflow for processingpreauthorized financial transactions in an ecosystem, such as theecosystem shown in FIG. 2.

FIG. 8 is a block diagram illustrating an example operating environmentin which financial transactions may be processed.

Corresponding reference characters indicate corresponding partsthroughout the drawings.

DETAILED DESCRIPTION

The subject matter described herein relates to processing one or moreautomated banking machine-related financial transactions. Embodiments ofthe disclosure enable a cardholder to obtain authorization of afinancial transaction prior to realizing or carrying out the financialtransaction at an automated banking machine, such as an automated tellermachine (ATM). The financial transaction may be preauthorized, forexample, in a trusted environment. For example, a user device associatedwith the cardholder may be used to enter into the financial transactionand/or obtain authorization of the financial transaction. In thismanner, the cardholder may approach the automated banking machine withincreased confidence that the interaction with the automated bankingmachine will be favorable, quick, and efficient. At least someembodiments described herein preauthorize financial transactions and/orcarry out the preauthorized financial transactions in accordance with anonvisual communication program.

While no personally identifiable information is tracked by theembodiments described herein, the embodiments have been described withreference to data being monitored and/or collected from one or moreusers (e.g., the cardholder). The data may be monitored and/or collectedin accordance with applicable data privacy laws and regulations. Forexample, notice may be provided to the users (e.g., via a dialog box orpreference setting), and/or users may be given the opportunity to giveor deny consent for the monitoring and/or collection of the data. Theconsent may take the form of opt-in consent or opt-out consent.

Aspects of the disclosure provide for a computing system that performsone or more operations in an environment including a plurality ofdevices coupled to each other via a network (e.g., a local area network(LAN), a wide area network (WAN), the Internet). For example, a cashiersystem may communicate with a user device and/or a financial transactionprocessing computing device to perform one or more operations in afinancial transaction processing environment. In some embodiments, thecashier system facilitates dataflow between the user device and thefinancial transaction processing computing device to enable a cardholderto obtain preauthorization of a financial transaction and carry out thepreauthorized financial transaction at an automated banking machineefficiently and effectively.

The systems and processes described herein may be implemented usingcomputer programming or engineering techniques including computersoftware, firmware, hardware or a combination or subset thereof. Atleast one technical problem with known computing systems is that it canbe risky, tedious, and/or time-consuming to process at least somefinancial transactions. The embodiments described herein address atleast this technical problem. By preauthorizing financial transactionsand carrying out the preauthorized financial transactions in the mannerdescribed in this disclosure, some embodiments reduce fraud and/orprocessing costs, increase user efficiency and/or user confidence,and/or improve user experience and/or user interaction performance.Additionally, some embodiments improve data integrity, data transmissionsecurity, and/or communication between systems by allowing a financialtransaction to be authorized in a trusted environment; and/or reduceerror rate by automating at least a portion of the transactionauthorization process. Moreover, some embodiments may facilitateimproving processor speed, processor security, and/or operating systemresource allocation.

The technical effect of the systems and processes described herein isachieved by performing at least one of the following operations: a)analyzing a request for preauthorization of a financial transaction; b)determining a transaction timeframe and a machine identifier; c)analyzing user location data and machine location data to identify atransaction timeframe; d) analyzing user location data and time data toidentify a cash machine; e) generating a prompt to select a set of cashmachines; f) analyzing user input associated with a selection of the setof cash machines; g) determining whether to process the financialtransaction in accordance with a nonvisual communication program; h)generating an instruction to identify a capture time associated with thefinancial transaction, i) generating an instruction to determine whetherthe capture time satisfies the transaction timeframe; j) generating aninstruction to dispense the transaction amount of cash; k) determiningwhether a hold duration associated with the financial transactionexceeds a hold threshold; l) generating a request to modify thetransaction timeframe and/or identify another cash machine; m) analyzingposition data to determine whether a user device or access card isproximate to the cash machine; n) detecting a transmission associatedwith an object; o) scanning a predetermined scan area to generate scandata associated with an object; p) analyzing the scan data to identifyan identifier associated with the object; q) determining whether theobject is associated with the cardholder account; and r) identifying anotification indicative of the transaction amount of cash beingdispensed.

FIG. 1 is a block diagram illustrating an example environment 100 forprocessing one or more financial transactions. The environment 100includes a processing network 110, such as the MASTERCARD® brand paymentprocessing network (MASTERCARD® is a registered trademark of MasterCardInternational Incorporated located in Purchase, N.Y.). The MASTERCARD®brand payment processing network is a propriety network for exchangingfinancial transaction data between members of the MASTERCARD® brandpayment processing network.

The environment 100 includes one or more merchants 120 that acceptpayment via the processing network 110. To accept payment via theprocessing network 110, the merchant 120 establishes a financial accountwith an acquirer 130 that is a member of the processing network 110. Theacquirer 130 is a financial institution that maintains a relationshipwith one or more merchants 120 to enable the merchants 120 to acceptpayment via the processing network 110. The acquirer 130 may also beknown as an acquiring bank, a processing bank, or a merchant bank.

The environment 100 includes one or more issuers 140 that issue orprovide one or more payment cards 150 to one or more cardholders 160 or,more broadly, account holders (“cardholder” and “account holder” may beused interchangeably herein). An issuer 140 is a financial institutionthat maintains a relationship with a cardholder 160 to enable thecardholder 160 to make a payment using a payment card 150 via theprocessing network 110. As described herein, the term “payment card”includes credit cards, debit cards, prepaid cards, key fobs, digitalcards, smart cards, and any other payment product that is linked orassociated with a corresponding cardholder account maintained by theissuer 140.

The cardholder 160 may use the payment card 150 to enter into one ormore financial transactions with one or more merchants 120. The paymentcard 150 may have any shape, size, or configuration that enables thecardholder 160 to make a payment to a merchant 120 using a cardholderaccount. For example, account information stored in a microchip ormagnetic stripe on the payment card 150 may be used to identify acardholder account associated with the payment card 150. In someembodiments, the payment card 150 uses mobile payment technology and/orcontactless payment technology to facilitate communication between thecardholder 160 and the merchant 120. For example, the payment card 150may include or be associated with a radio frequency identification(RFID)-enabled device, a BLUETOOTH® brand wireless technology-enableddevice, a WI-FI® brand local area wireless computing network-enableddevice, and/or a near field communication (NFC) wirelesscommunication-enabled device. (BLUETOOTH® is a registered trademark ofBluetooth Special Interest Group, and WI-FI® is a registered trademarkof the Wi-Fi Alliance).

In some embodiments, the cardholder 160 presents the merchant 120 withthe payment card 150 to make a payment to the merchant 120 using thecardholder account in exchange for the good or service. Alternatively,the cardholder 160 may provide the merchant 120 with account informationassociated with the payment card 150 without physically presenting thepayment card 150 to the merchant 120 (e.g., for remote financialtransactions, including e-commerce transactions, card-not-presenttransactions, or card-on-file transactions). Account information mayinclude, for example, a name of the cardholder 160, an account number,an expiration date, and/or a security code (e.g., a card verificationvalue (CVV), a card verification code (CVC), a personal identificationnumber (PIN)).

The merchant 120 requests authorization from an acquirer 130 for atleast the amount of the purchase. The merchant 120 may requestauthorization using any financial transaction computing deviceconfigured to transmit account information of the cardholder 160 to oneor more financial transaction processing computing devices of theacquirer 130. For example, the merchant 120 may use a point-of-sale(POS) terminal that reads account information from the microchip ormagnetic stripe on the payment card 150 and transmits the accountinformation to a financial transaction processing computing device ofthe acquirer 130. Additionally or alternatively, the POS terminal mayreceive the account information from a communication device using mobilepayment technology and/or contactless payment technology, and transmitthe account information to the financial transaction processingcomputing device of the acquirer 130.

Using the processing network 110, the financial transaction processingcomputing device of the acquirer 130 communicates with one or morefinancial transaction processing computing devices of an issuer 140 todetermine whether the account information of the cardholder 160 matchesor corresponds to the account information of the issuer 140, whether thecardholder account is in good standing, and/or whether the purchase iscovered by an available credit line or account balance associated withthe cardholder account (e.g., a purchase amount is less than an accountcapacity). Based on these determinations, a financial transactionprocessing computing device of the issuer 140 determines whether toapprove or decline the request for authorization from the merchant 120.

If the request for authorization is declined, the merchant 120 isnotified (e.g., via the processing network 110) as such, and may requestauthorization from the acquirer 130 for a lesser amount or request analternative form of payment (e.g., cash, another payment card 150) fromthe cardholder 160. If the request for authorization is approved, anauthorization code is issued (e.g., via the processing network 110) tothe merchant 120, and the available credit line or account balanceassociated with the cardholder account is decreased by at least theamount of the purchase. The financial transaction is then settledbetween the merchant 120, the acquirer 130, the issuer 140, and/or thecardholder 160. Settlement typically includes the acquirer 130reimbursing the merchant 120 for selling the good or service, and theissuer 140 reimbursing the acquirer for reimbursing the merchant 120.When a credit card is used, the issuer 140 may bill the cardholder 160to settle the cardholder account (e.g., a credit card account) with thecardholder 160. When a debit or prepaid card is used, the issuer 140 mayautomatically withdraw funds from the cardholder account (e.g., achecking account, a savings account) to settle the cardholder account.

FIG. 2 is a block diagram illustrating an example ecosystem 200 forallowing a user 202 (e.g., cardholder 160) to obtain preauthorization ofone or more financial transactions and/or carry out the preauthorizedfinancial transactions in the environment 100. The user 202 may use auser device 210 to enter into a financial transaction (e.g., a firstfinancial transaction).

The user device 210 includes one or more memory devices orcomputer-readable media 212 storing computer-executable instructions,and one or more processors 214 configured to execute thecomputer-executable instructions to perform one or more operations, suchas obtain account information associated with the user 202. In someembodiments, a processor 214 executes or runs one or more applications(apps) to perform the operations. A payment card app, for example, maybe used to enter into a financial transaction. A global positioningsystem (GPS) app, for another example, may be used to identify aposition of the user device 210.

The user device 210 may use one or more interfaces 216 to presentinformation to and/or receive user input from a user of the user device210 (e.g., user 202). For example, an interface 216 may be used toreceive user input indicative of the account information. The interfaces216 may also be used to transmit data to and/or receive data from one ormore other computing systems. For example, an interface 216 may be usedto transmit account information to a cashier system 220 for facilitatingthe financial transaction. The user device 210 may include an instanceof an application (e.g., a client-side application) that enables theuser device 210 to communicate with another computing system (e.g., acloud-computing provider) that performs one or more backend operationsusing a counterpart application (e.g., server-side application) and/orthrough one or more server-side services.

The cashier system 220 includes a merchant device 230 configured toobtain the account information for facilitating the financialtransaction. The merchant device 230 may be associated, for example,with a retailer or a financial institution. The merchant device 230includes one or more memory devices or computer-readable media 232storing computer-executable instructions, and one or more processors 234configured to execute the computer-executable instructions to performone or more operations, such as generate a request for preauthorizationof the financial transaction. In some embodiments, a processor 234executes or runs one or more applications to perform the operations. Apayment card app, for example, may be used to facilitate the financialtransaction.

The merchant device 230 may use one or more interfaces 236 to presentinformation to and/or receive user input from a user of the merchantdevice 230 (e.g., merchant 120). The interfaces 236 may also be used totransmit data to and/or receive data from one or more other computingsystems (e.g., user device 210). For example, an interface 236 may beused to receive the account information from the user device 210. Foranother example, an interface 236 may be used to transmit the requestfor preauthorization to a system server 240 (e.g., a financialtransaction processing computing device of an issuer 140) for processingthe financial transaction.

The merchant device 230 may include a server-side application thatenables one or more client-side services to be provided at one or moreother computing systems (e.g., user device 210). Additionally oralternatively, the merchant device 230 may include a client-sideapplication that enables the merchant device 230 to communicate with acloud-computing provider (e.g., the system server 240) that performs oneor more backend operations using a server-side application and/orthrough one or more server-side services.

The system server 240 is configured to obtain the request forpreauthorization for processing the financial transaction. The systemserver 240 includes one or more memory devices or computer-readablemedia 242 storing computer-executable instructions, and one or moreprocessors 244 configured to execute the computer-executableinstructions to perform one or more operations, such as generate one ormore preauthorization messages associated with the financialtransaction. Preauthorization messages may include, for example, anotification, an instruction, a prompt, and the like. In someembodiments, a processor 244 executes or runs one or more applicationsto perform the operations. A payment card app, for example, may be usedto process the financial transaction.

The system server 240 may use one or more interfaces 246 to presentinformation to and/or receive user input from a user of the systemserver 240 (e.g., issuer 140). The interfaces 246 may also be used totransmit data to and/or receive data from the other computing systems(e.g., user device 210, merchant device 230). For example, an interface246 may be used to receive the request for preauthorization from thecashier system 220. For another example, an interface 246 may be used totransmit a preauthorization message to the user device 210 used to enterinto the financial transaction, another user device 210 associated withthe user 202 (e.g., a mobile device), and/or the cashier system 220 forcarrying out the financial transaction.

The system server 240 may include a server-side application that enablesone or more client-side services to be provided at one or more othercomputing systems (e.g., user device 210, merchant device 230).Additionally or alternatively, the system server 240 may include aclient-side application that enables the system server 240 tocommunicate with a cloud-computing provider that performs one or morebackend operations using a server-side application and/or through one ormore server-side services.

The cashier system 220 includes one or more cash machines 250 configuredto obtain the preauthorization message for carrying out the financialtransaction. A cash machine 250 may be included in, coupled to, and/orassociated with the merchant device 230. The cash machine 250 includesone or more memory devices or computer-readable media 252 storingcomputer-executable instructions, and one or more processors 254configured to execute the computer-executable instructions to performone or more operations, such as carry out the financial transaction. Insome embodiments, a processor 254 executes or runs one or moreapplications to perform the operations. A payment card app, for example,may be used to carry out the financial transaction. A GPS app, foranother example, may be used to identify a position of the cash machine250.

The cash machine 250 may use one or more interfaces 256 to transmit datato and/or receive data from the other computing systems (e.g., userdevice 210, merchant device 230, system server 240). For example, aninterface 256 may be used to receive a preauthorization message from themerchant device 230 and/or system server 240. The interfaces 256 mayalso be used to present information to and/or receive user input from auser of the cash machine 250 (e.g., merchant 120, user 202). Forexample, an interface 256 may be used to present a preauthorizationmessage to the user of the cash machine 250.

A manned cash machine 250 enables a user affiliated with the merchant120, such as a cashier at a retailer or a teller at a financialinstitution, to service a customer or client of the merchant 120 (e.g.,user 202) for carrying out the financial transaction. An automated cashmachine 250, such as a self-serve kiosk at a retailer or an automatedbanking machine (e.g., ATM) at a financial institution, enables the user202 to carry out the financial transaction with little or no assistancefrom a user affiliated with the merchant 120.

The cash machine 250 may include a client-side application that enablesthe cash machine 250 to communicate with a cloud-computing provider(e.g., merchant device 230, system server 240) that performs one or morebackend operations using a server-side application and/or through one ormore server-side services. For example, a thin client included in,coupled to, and/or associated with the cash machine 250 may provideremote access to the merchant device 230 and/or system server 240 forperforming one or more backend operations.

The ecosystem 200 includes one or more communication networks 260 thatenable information to be communicated between a plurality of computingor communication systems coupled to the communication networks 260(e.g., user device 210, cashier system 220, merchant device 230, systemserver 240, cash machine 250). Example communication networks 260include a cellular or mobile network and the Internet. Alternatively,the communication networks 260 may include any communication medium thatenables the ecosystem 200 to function as described herein including, forexample, a personal area network (PAN), a LAN, and/or a WAN.

FIG. 3 is a block diagram illustrating an example computing system 300that may be used to process one or more preauthorized financialtransactions in the ecosystem 200. A user 202 may use a user device 210to obtain authorization to withdraw or obtain cash at a cash machine 250remote from the user device 210. Cash may be obtained, for example,through a cash withdrawal action that allows funds to be withdrawn froma user account (e.g., checking account, savings account) and/or througha cash disbursement action that allows funds to be “purchased” using theuser account (e.g., credit card account).

The user device 210 may be used to provide a merchant device 230associated with the cash machine 250 with account information associatedwith an access card 310 (e.g., payment card 150), such as a cardholderidentifier 312. The account information may be provided withoutphysically presenting the payment card 150 to the merchant device 230and/or to the cash machine 250. The access card 310 may be, for example,an EMV® brand smart card. (EMV® is a registered trademark of EMVCo,LLC). In some embodiments, the account information includes dataindicative of an enrollment status associated with a nonvisualcommunication program. The merchant device 230 uses the accountinformation to generate a request for preauthorization of a financialtransaction, and transmits the request to a system server 240 forprocessing the financial transaction. The request may include, forexample, the account information and a transaction amount 314.

In response to receiving the request for preauthorization, the systemserver 240 analyzes the request to identify the cardholder identifier312, and uses the cardholder identifier 312 to identify a cardholderaccount 320 associated with the cardholder identifier 312. Thecardholder account 320 may be identified or selected, for example, fromone or more cardholder accounts stored and/or maintained at the systemserver 240. In some embodiments, the system server 240 identifies, fromthe cardholder accounts, a first cardholder account (e.g., cardholderaccount 320) associated with credential data 322 that matches orcorresponds to the cardholder identifier 312. Credential data 322includes any data that enables an entity (e.g., user 202, user device210) to be identified and/or authenticated. Credential data 322 mayinclude, for example, an account number, a username, a PIN, a password,a public key infrastructure (PKI) certificate, a token, biometric data,and the like.

The system server 240 uses account data associated with the cardholderaccount 320 to process the financial transaction. In some embodiments,the system server 240 identifies an account threshold (e.g., anavailable credit line, an available account balance) associated with thecardholder account 320, and determines whether the transaction amount314 exceeds the account threshold. If the transaction amount 314 is lessthan or equal to the account threshold, the system server 240 approvesthe request for preauthorization, reserves or allocates preauthorizedfunds, and generates a response to the request in accordance with theapproval. The response may include, for example, a preauthorization code324 that may be used to authenticate a holder of the preauthorizationcode 324 for obtaining or capturing the preauthorized funds. If thetransaction amount 314 is greater than the account threshold, the systemserver 240 declines the request for preauthorization and generates aresponse to the request in accordance with the declination.

Preauthorized funds may be obtained or captured at a cash machine 250,for example, to realize or carry out the financial transaction. In someembodiments, the system server 240 identifies or determines atransaction timeframe 332 in which the preauthorized funds may becaptured for carrying out the financial transaction. Additionally, thesystem server 240 may identify or determine one or more machineidentifiers 334 associated with one or more cash machines 250 at whichthe preauthorized funds may be captured for carrying out the financialtransaction. The transaction timeframe 332 and/or machine identifiers334 may be determined based on time data 336, machine location data 338associated with one or more geolocations of the cash machines 250,and/or user location data 340 associated with a geolocation of the user202. In some embodiments, the system server 240 identifies and/orgenerates the time data 336, machine location data 338, and/or userlocation data 340 based on user input. For example, the request forpreauthorization may be analyzed to identify and/or generate the timedata 336, machine location data 338, and/or user location data 340. Foranother example, the user 202 may be prompted to identify a desired timeand/or geolocation.

In some embodiments, the system server 240 identifies and/or generatesthe user location data 340 based on position data 342 (e.g., GPS data).The position data 342 may be associated with an object that isassociated with the user 202, such as the user device 210 or the accesscard 310. Contact data 344 associated with the cardholder account 320,for example, may be used to communicate with one or more user devices210 associated with the user 202 for obtaining the position data 342.Contact data 344 includes any data that enables an entity (e.g., user202, user device 210) to be located and/or approached for communicatingwith the entity. Contact data 344 may include, for example, a telephonenumber, a BLUETOOTH® brand wireless technology identifier, a routingnumber, an Internet Protocol (IP) address, a media access controller(MAC) address, an NFC identifier, an RFID identifier, and the like.

The time data 336, machine location data 338, and/or user location data340 may be identified, generated, and/or modified in accordance withpreference data 346 associated with the cardholder account 320.Preference data 346 may be indicative of one or more tastes, tendencies,or biases of an entity (e.g., user 202). Tastes, tendencies, and/orbiases may be expressed by the user 202 (e.g., via user input) orimplied based on other data associated with the user 202. For example, atransaction history indicative of a repeated time and/or geolocation maybe indicative of a preference for the repeated time and/or geolocation.

The system server 240 generates one or more preauthorization messagesthat enable the user 202 to carry out the financial transaction withinthe transaction timeframe 332 and/or at a predetermined cash machine250. The preauthorization messages may include, for example, a machineinstruction 352 and/or a user instruction 354. The machine instruction352 may be transmitted to one or more predetermined cash machines 250such that the predetermined cash machines 250 are configured to performone or more operations for carrying out the financial transaction. Theuser instruction 354 may be transmitted to the user device 210 used toenter into the financial transaction, a user device 210 different fromthe user device 210 used to enter into the financial transaction, and/orthe predetermined cash machines 250 such that a user device 210 and/or apredetermined cash machine 250 is configured to present the userinstruction 354 to the user 202.

The user 202 may follow the user instruction 354 to capture thepreauthorized funds within the transaction timeframe 332 at apredetermined cash machine 250. In some embodiments, the cashier system220 (e.g., merchant device 230, cash machine 250) identifies a capturetime 362 associated with a moment the preauthorized funds are captured.The capture time 362 may be identified, for example, upon receiving thepreauthorization code 324. The capture time 362 may also be identified,for another example, upon identifying that the user 202 is proximate tothe predetermined cash machine 250.

In some embodiments, the cashier system 220 scans a predetermined scanarea proximate to the cash machine 250 to generate scan data, andanalyzes the scan data to determine whether the user 202 is proximate tothe predetermined cash machine 250. For example, the cashier system 220may generate scan data associated with a user device 210 and/or accesscard 310 presented to the cash machine 250 for capturing thepreauthorized funds. For another example, the cashier system 220 maygenerate scan data associated with the user 202, user device 210, and/oraccess card 310 approaching the cash machine 250 for capturing thepreauthorized funds. The scan data may be analyzed to authenticate theuser 202 in the predetermined scan area as being authorized to capturethe preauthorized funds. Additionally or alternatively, the cashiersystem 220 receives position data 342 associated with the user device210 and/or access card 310, and analyzes the position data 342 todetermine whether the user 202 is proximate to the predetermined cashmachine 250 for authenticating the user 202.

Upon identifying the capture time 362, the cashier system 220 determineswhether the capture time 362 satisfies the transaction timeframe 332. Ifthe capture time 362 is less than or equal to the transaction timeframe332 (e.g., the transaction timeframe 332 has not expired or “timedout”), the cash machine 250 dispenses an amount of cash associated withthe transaction amount 314. In some embodiments, the cash machine 250dispenses the amount of cash in accordance with a denomination breakdown372. The denomination breakdown 372 may be included in the machineinstruction 352. For example, the denomination breakdown 372 may beidentified based on the request for preauthorization and/or preferencedata 346. Alternatively, the user 202 may be prompted to identify adesired denomination breakdown 372.

Upon dispensing the amount of cash associated with the transactionamount 314, the cashier system 220 generates and transmits anotification 374 that is indicative of the amount of cash beingdispensed. The notification 374 may be received, for example, at thesystem server 240 to enable the system server 240 to recognize oridentify the financial transaction as being realized or carried out. Oncondition that a capture time 362 is not or yet to be identified, thecashier system 220 and/or system server 240 may periodically (e.g., eachpredetermined interval of time) and/or systematically (e.g., eachpredetermined occurrence) determine whether a hold duration 376associated with the preauthorized funds satisfies one or morepredetermined hold thresholds 378.

If the hold duration 376 exceeds a predetermined hold threshold 378, thetransaction timeframe 332 may be extended or increased and/or amore-proximate or more-convenient cash machine 250 may be identified. Insome embodiments, the cashier system 220 and/or system server 240communicates with the user device 210 to prompt the user 202 to modifythe transaction timeframe 332 and/or identify another cash machine 250.If the hold duration 376 exceeds the transaction timeframe 332 (e.g., acapture time 362 is not identified before the transaction timeframe 332expires or “times out”), the preauthorized funds are released to enablethe system server 240 to allocate the funds towards another financialtransaction, including another preauthorized financial transaction.

In some embodiments, the cashier system 220 and/or system server 240determines whether to process the financial transaction in accordancewith a nonvisual communication program. For example, the cashier system220 and/or system server 240 may determine whether the cardholderaccount 320 is enrolled in or associated with a nonvisual communicationprogram. If the cardholder account 320 is associated with the nonvisualcommunication program, the cashier system 220 and/or system server 240communicates with the user 202 using nonvisual communication (e.g., atthe user device 210, the merchant device 230, and/or the cash machine250). A cardholder account may be enrolled in the nonvisualcommunication program, for example, if a user of the cardholder accountis blind or prefers to communicate using one or more nonvisualcommunications, such as an audible communication and/or a tactilecommunication. In some embodiments, the cashier system 220 and/or systemserver 240 uses or analyzes preference data 346 to identify anenrollment status of the cardholder account 320.

FIG. 4 is a flowchart illustrating an example method 400 for processinga preauthorized financial transaction in the ecosystem 200 using acomputing system (e.g., merchant device 230, system server 240). Arequest for preauthorization of a financial transaction is identified at410. The request for preauthorization may be generated at and/orreceived from, for example, a cashier system 220. In some embodiments,the request for preauthorization includes a cardholder identifier 312and a transaction amount 314.

Upon approving the request for preauthorization, a transaction timeframe332 in which preauthorized funds may be captured is determined at 420,and one or more cash machines 250 at which the preauthorized funds maybe captured are identified at 430. The transaction timeframe 332 and/orcash machines 250 may be determined and/or identified based on one ormore communications with the user device 210. For example, the requestfor preauthorization may be analyzed to identify the transactiontimeframe 332, one or more machine identifiers 334, time data 336,machine location data 338, and/or user location data 340. For anotherexample, position data 342 associated with the user device 210 and/oraccess card 310 may be received. For yet another example, a user of theuser device 210 (e.g., user 202) may be prompted to identify a desiredtime and/or geolocation for capturing the preauthorized funds. In someembodiments, preference data 346 associated with a cardholder account320 used to enter into the financial transaction may be used todetermine, identify, and/or modify the transaction timeframe 332,machine identifiers 334, time data 336, machine location data 338,and/or user location data 340.

Preference data 346 may also be used to determine whether to process thefinancial transaction in accordance with a nonvisual communicationprogram. For example, preference data 346 may be used to determine at440 whether the cardholder account 320 is associated with the nonvisualcommunication program. If the cardholder account 320 is not enrolled inthe nonvisual communication program, an instruction is generated at 450to dispense cash in a conventional manner. For example, the instructionmay configure the cash machine 250 to use visual prompts and/orinstructions for carrying out the financial transaction.

On the other hand, if the financial transaction is to be processed inaccordance with the nonvisual communication program (e.g., if thecardholder account 320 is enrolled in the nonvisual communicationprogram), a machine instruction 352 is generated at 460 to dispense cashin accordance with the nonvisual communication program. For example, themachine instruction 352 may configure the cash machine 250 to usenonvisual prompts and/or instructions for carrying out the financialtransaction. For another example, the machine instructions 352 mayconfigure the cash machine 250 to dispense cash in a manner that allowsthe user 202 to confirm or verify that the transaction amount 314 ofcash was dispensed from the cash machine 250 using nonvisual cues.

FIG. 5 is a block diagram illustrating a computing system 500 (e.g.,cashier system 220, system server 240) including an interface component510, an account component 520, a preauthorization component 530, anidentification component 540, a detection component 550, a dispensercomponent 560, and/or a modification component 570 that may be used toprocess one or more preauthorized financial transactions in theecosystem 200.

In some embodiments, the interface component 510 enables the computingsystem 500 to receive data from and/or transmit data to one or moreother computing systems (e.g., user device 210, cashier system 220,merchant device 230, system server 240, cash machine 250). For example,the interface component 510 may be coupled to another computing systemto facilitate communication between the other computing system and theaccount component 520, the preauthorization component 530, theidentification component 540, the detection component 550, the dispensercomponent 560, and/or the modification component 570. In someembodiments, the interface component 510 facilitates communicationbetween and among the account component 520, the preauthorizationcomponent 530, the identification component 540, the detection component550, the dispenser component 560, and/or the modification component 570.

The account component 520 enables the computing system 500 to managedata associated with one or more accounts (e.g., cardholder account320). Account data stored and/or maintained at or by the computingsystem 500 may include data registered with the computing system 500,such as credential data 322, contact data 344, and/or preference data346. In some embodiments, the account component 520 uses credential data322 to selectively allow one or more users (e.g., user 202) to accessand use account data associated with the cardholder account 320. Forexample, the credential data 322 may be used to authenticate the user202 as being an authorized user of the cardholder account 320. In someembodiments, the account component 520 uses contact data 344 tocommunicate with one or more other computing systems associated with thecardholder account 320 (e.g., user device 210). For example, contactdata may be used to locate and/or approach a user device 210 forcommunicating with a user of the user device 210 (e.g., user 202).

The account component 520 is configured to process one or moreregistration requests to register data with the computing system 500.Various identifiers (e.g., biometric identifier, device identifier, cardidentifier), for example, may be registered with the computing system500 to associate a user 202, a user device 210, and/or an access card310 with the cardholder account 320. For another example, userpreferences may be registered with the computing system 500 to enroll anentity (e.g., user 202, user device 210, access card 310) and/or anaccount (e.g., cardholder account 320) in a nonvisual communicationprogram. The account component 520 is configured to register data withthe computing system 500 such that the interface component 510, accountcomponent 520, the preauthorization component 530, the identificationcomponent 540, the detection component 550, the dispenser component 560,and/or the modification component 570 may access and/or use the data inan efficient manner.

The preauthorization component 530 enables the computing system 500 toidentify a preauthorized financial transaction and an account associatedwith the preauthorized financial transaction. The preauthorizationcomponent 530 is configured to communicate (e.g., via the interfacecomponent 510) with another computing system (e.g., user device 210,cashier system 220, merchant device 230, system server 240, cash machine250) to obtain a message associated with a financial transaction, suchas a request for preauthorization and/or a preauthorization message(e.g., machine instruction 352). A message may indicate that thefinancial transaction is associated with a nonvisual communicationprogram. In some embodiments, the preauthorization component 530identifies a transaction amount 314 and an account associated with thefinancial transaction (e.g., cardholder account 320).

The identification component 540 enables the computing system 500 toidentify one or more parameters associated with a preauthorizedfinancial transaction. The identification component 540 is configured tocommunicate with the account component 520 (e.g., via the interfacecomponent 510) to access the cardholder account 320 to identify accountdata (e.g., credential data 322, contact data 344, preference data 346)registered with the computing system 500. In some embodiments, theidentification component 540 identifies a transaction timeframe 332 inwhich preauthorized funds may be captured and/or one or more cashmachines 250 at which the preauthorized funds may be captured. Thetransaction timeframe 332 and/or cash machines 250 may be identifiedand/or determined based on time data 336, machine location data 338and/or user location data 340.

For example, a current location (e.g., based on user location data 340),a destination (e.g., based on machine location data 338), and a travelrate for traversing a distance between a geolocation of the user 202 anda geolocation of the cash machine 250 may be used to determine thetransaction timeframe 332. For another example, a current location(e.g., based on user location data 340), a travel time (e.g., based ontime data 336), and a travel rate may be used to determine an areaaround a geolocation of the user 202 that is traversable within theamount of time associated with the time data 336. The area may beanalyzed to identify one or more cash machines 250 physically located inthe area. If a plurality of cash machines 250 are identified, aplurality of machine identifiers 334 associated with the identified cashmachines 250 may be transmitted to a user device 210 for prompting theuser 202 to select or identify, from the plurality of cash machines 250,a set of cash machines 250 at which the preauthorized funds may becaptured.

The detection component 550 enables the computing system 500 toauthenticate a user proximate to the cash machine 250 as an authorizeduser of an account (e.g., cardholder account 320). In some embodiments,the detection component 550 determines whether a cardholder (e.g., user202) of an account associated with a preauthorized financial transaction(e.g., cardholder account 320) is proximate to the cash machine 250.Upon determining that the user 202 is proximate to the cash machine 250,the detection component 550 identifies a capture time 362 associatedwith the preauthorized financial transaction, and determines whether thecapture time 362 satisfies the transaction timeframe 332.

For example, a transmission may be detected and analyzed to determinewhether a source of the transmission (e.g., user device 210, access card310) is associated with the cardholder account 320. The transmission mayinclude or indicate an identifier associated with the source (e.g.,device identifier, card identifier). Additionally or alternatively, scandata associated with one or more objects detected in a predeterminedscan area may be analyzed to identify one or more identifiers (e.g.,biometric identifier, device identifier, card identifier). The detectioncomponent 550 compares one or more identifiers with account dataregistered with the computing system 500 (e.g., credential data 322,contact data 344). If an identifier matches or corresponds to credentialdata 322 and/or contact data 344, the user 202 is determined to beproximate to the cash machine 250.

For another example, position data 342 associated with a user device 210and/or access card 310 associated with the cardholder account 320 isobtained. Contact data 344 registered with the computing system 500, forexample, may be used to identify the user device 210 and/or access card310 and communicate with the user device 210 and/or access card 310 forobtaining the position data 342. The detection component 550 analyzesthe position data 342 to determine whether the user 202 is proximate tothe cash machine 250. If a geolocation associated with the position data342 (e.g., a device location) is proximate to a geolocation associatedwith the cash machine 250 (e.g., a machine location), the user 202 isdetermined to be proximate to the cash machine 250.

The dispenser component 560 enables the computing system 500 to dispensecash in accordance with the nonvisual communication program. In someembodiments, the dispenser component 560 obtains a denominationbreakdown 372 corresponding to a transaction amount 314, and dispensesthe transaction amount 314 of cash in accordance with the denominationbreakdown 372. In some embodiments, the dispenser component 560dispenses cash in a predetermined order, grouping, cadence, or timing ofdenominations that allows the user 202 to confirm or verify that thetransaction amount 314 of cash was dispensed. Upon dispensing thetransaction amount 314 of cash, the dispenser component 560 generates anotification 374 that is indicative of the transaction amount 314 ofcash being dispensed.

The modification component 570 enables the computing system 500 tomodify the transaction timeframe 332 in which the preauthorizedfinancial transaction may be carried out and/or identify another cashmachine 250 at which the preauthorized financial transaction may becarried out. In some embodiments, the modification component 570determines whether a hold duration 376 associated with the preauthorizedfinancial transaction exceeds a predetermined hold threshold 378. If thehold duration 376 exceeds the predetermined hold threshold 378, themodification component 570 generates a request to modify the transactiontimeframe 332 and/or identify another cash machine 250.

FIG. 6 is a sequence diagram illustrating an example method 600 forprocessing a preauthorized financial transaction in the ecosystem 200.In some embodiments, a user device 210 transmits at 602 accountinformation and a transaction amount 314 to a merchant device 230. Themerchant device 230 uses the account information and the transactionamount 314 to generate at 605 a request for preauthorization. Therequest for preauthorization is transmitted at 606 to a system server240 for processing.

Upon receiving the request for preauthorization, the system server 240identifies at 610 a cardholder account 320 used to enter into thefinancial transaction. The request for preauthorization may be analyzedto determine whether to approve the request for preauthorization. If therequest for preauthorization is approved, the system server 240determines at 615 a transaction timeframe 332 in which the financialtransaction may be carried out and one or more cash machines 250 atwhich the preauthorized funds may be captured.

In some embodiments, the system server 240 identifies at 620 that thecardholder account 320 is enrolled in a nonvisual communication program.Upon identifying that the cardholder account 320 is enrolled in thenonvisual communication program, the system server 240 generates at 625a machine instruction 352 and a user instruction 354 in accordance withthe nonvisual communication program, and transmits at 626 a response tothe request for preauthorization, including the machine instruction 352and the user instruction 354, to the merchant device 230. Alternatively,the merchant device 230 may identify that the cardholder account 320 isenrolled in the nonvisual communication program, and generate themachine instruction 352 and/or the user instruction 354 in accordancewith the nonvisual communication program.

The merchant device 230 transmits at 628 the machine instruction 352 toa cash machine 250, and transmits at 629 the user instruction 354 to theuser device 210. Alternatively, the system server 240 may transmit themachine instruction 352 directly to the cash machine 250, and/ortransmit the user instruction 354 directly to the user device 210. Theuser device 210 presents at 630 the user instruction 354 to a user ofthe user device 210 (e.g., user 202) to enable the user to carry out thefinancial transaction. In some embodiments, the user instruction 354 istransmitted to a user device 210 associated with the cardholder account320 other than the user device 210 used to enter into the financialtransaction (e.g., a mobile device) for presentation.

Upon receiving the machine instruction 352, the cash machine 250 isconfigured to carry out the financial transaction in accordance with thenonvisual communication program. The cash machine 250 identifies at 640a capture time 362 that is indicative of the user 202 being proximate tothe cash machine 250, and dispenses at 645 cash to the user 202. Thecash may be dispensed, for example, in accordance with a denominationbreakdown 372. Upon dispensing the cash, the cash machine 250 generatesat 650 a notification 374 associated with the dispensed cash, andtransmits at 652 the notification 374 to the merchant device 230. Themerchant device 230 transmits at 654 the notification 374 to the systemserver 240 to enable the system server 240 to identify that thefinancial transaction is carried out. In some embodiments, the cashmachine 250 transmits the notification 374 directly to the system server240.

FIG. 7 is a flow diagram illustrating an example dataflow 700 forpreauthorizing a financial transaction and carrying out thepreauthorized financial transaction in the ecosystem 200. The dataflow700 includes a preauthorization phase 710, in which a request forpreauthorization of a financial transaction is processed, and arealization phase 720, in which a preauthorized financial transaction iscarried out.

During the preauthorization phase 710, a user 202 may use a client-sideapplication 730 (e.g., at a user device 210) to preauthorize anautomated banking machine-related financial transaction. The client-sideapplication 730 may be used, for example, to provide a cardholderidentifier 312 and a transaction amount 314 for generating a request forpreauthorization. A server-side application 740 (e.g., at the merchantdevice 230, at the system server 240) obtains the cardholder identifier312 and the transaction amount 314 from the client-side application 730,and identifies a cardholder account 320 associated with the cardholderidentifier 312 for processing the financial transaction. Credential data322 may be obtained from a memory area 750, and compared with thecardholder identifier 312 to identify the cardholder account 320.

The server-side application 740 determines a transaction timeframe 332in which the financial transaction may be carried out and one or morecash machines 250 at which preauthorized funds may be captured based ontime data 336, machine location data 338, and/or user location data 340.The time data 336, machine location data 338, and/or user location data340 may be identified and/or generated at the server-side application740. For example, the request for preauthorization may be analyzed toextract or identify time data 336, machine location data 338, and/oruser location data 340. For another example, position data 342 may beobtained from the client-side application 730 to identify a geolocationof a user 202 associated with the cardholder account 320 for generatinguser location data 340. For yet another example, machine location data338 may be obtained from one or more thin client applications (e.g., atone or more cash machines 250) to identify one or more geolocations ofthe cash machines 250 for generating machine location data 338. For yetanother example, preference data 346 may be obtained from the memoryarea 750 to identify, generate, and/or modify time data 336, machinelocation data 338, and/or user location data 340.

The server-side application 740 determines whether the cardholderaccount 320 is enrolled in a nonvisual communication program. Preferencedata 346 associated with the cardholder account 320, for example, may beused to determine an enrollment status. If the cardholder account 320 isenrolled in the nonvisual communication program, the server-sideapplication 740 generates a machine instruction 352 and a userinstruction 354 in accordance with the nonvisual communication program.

The machine instruction 352 enables the thin client application 760 toperform one or more operations for carrying out the financialtransaction. The user instruction 354 enables the client-sideapplication 730 to instruct a user of the client-side application 730(e.g., the user 202) to perform one or more operations for carrying outthe financial transaction. For example, the user 202 may approach a cashmachine 250 identified in the user instruction 354 within thetransaction timeframe 332 to capture the preauthorized funds at the cashmachine 250.

The dataflow 700 enters the realization phase 720 when a capture time362 is identified. The thin client application 760 may identify thecapture time 362 upon identifying a user 202 proximate to the cashmachine 250. Identifying a user 202, or an object associated with theuser 202, at the thin client application 760, for example, may beindicative of the user 202 being proximate to the cash machine 250. Insome embodiments, the thin client application 760 communicates with theclient-side application 730 to authenticate the user 202. If the capturetime 362 satisfies the transaction timeframe 332, cash is dispensed atthe cash machine 250 in accordance with the nonvisual communicationprogram. Upon identifying that the cash has been dispensed, the thinclient application 760 generates a notification 374 associated with thecash being dispensed. The notification 374 may be obtained, for example,at the server-side application 740.

FIG. 8 is a block diagram illustrating an example operating environment800 that may be used to process one or more financial transactions. Theoperating environment 800 is only one example of a computing andnetworking environment and is not intended to suggest any limitation asto the scope of use or functionality of the disclosure. The operatingenvironment 800 should not be interpreted as having any dependency orrequirement relating to any one or combination of components illustratedin the example operating environment 800.

The disclosure is operational with numerous other computing andnetworking environments or configurations. While some embodiments of thedisclosure are illustrated and described herein with reference to theoperating environment 800 being or including a merchant device 230(shown in FIG. 2), a system server 240 (shown in FIG. 2), a computingsystem 500 (shown in FIG. 5), and/or a server-side application 740(shown in FIG. 7), aspects of the disclosure are operable with anycomputing system (e.g., user device 210, cashier system 220, cashmachine 250, access card 310) that executes instructions to implementthe operations and functionality associated with the operatingenvironment 800.

For example, the operating environment 800 may include a mobile device,a tablet, a laptop computer, a desktop computer, a server computer, amicroprocessor-based system, a multiprocessor system, a communicationdevices in a wearable or accessory form factor (e.g., a watch, glasses,a headset, earphones, and the like), programmable consumer electronics,a portable media player, a gaming console, a set top box, a kiosk, atabletop device, an industrial control device, a minicomputer, amainframe computer, a network computer, a distributed computingenvironment that includes any of the above systems or devices, and thelike. The operating environment 800 may represent a group of processingunits or other computing systems. Additionally, any computing systemdescribed herein may be configured to perform any operation describedherein including one or more operations described herein as beingperformed by another computing system.

With reference to FIG. 8, an example system for implementing variousaspects of the disclosure may include a general purpose computing systemin the form of a computer 810. Components of the computer 810 mayinclude, but are not limited to, a processing unit 820 (e.g., aprocessor), a system memory 825 (e.g., a computer-readable storagedevice), and a system bus 830 that couples various system componentsincluding the system memory 825 to the processing unit 820. The systembus 830 may be any of several types of bus structures including a memorybus or memory controller, a peripheral bus, and a local bus using any ofa variety of bus architectures. By way of example, and not limitation,such architectures include Industry Standard Architecture (ISA) bus,Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, VideoElectronics Standards Association (VESA) local bus, and PeripheralComponent Interconnect (PCI) bus also known as Mezzanine bus.

The system memory 825 includes any quantity of media associated with oraccessible by the processing unit 820. For example, the system memory825 may include computer storage media in the form of volatile and/ornonvolatile memory, such as read only memory (ROM) 831 and random accessmemory (RAM) 832. The ROM 831 may store a basic input/output system(BIOS) 833 that facilitates transferring information between elementswithin computer 810, such as during start-up. The RAM 832 may containdata and/or program modules that are immediately accessible to and/orpresently being operated on by processing unit 820. For example, thesystem memory 825 may store computer-executable instructions,application data, transaction data, identifier data, profile data, timedata, location data, and other data. By way of example, and notlimitation, FIG. 8 illustrates operating system 834, applicationprograms 835, other program modules 836, and program data 837.

The computer 810 includes a variety of computer-readable media.Computer-readable media may be any available media that may be accessedby the computer 810 and includes both volatile and nonvolatile media,and removable and non-removable media. By way of example, and notlimitation, computer-readable media may comprise computer storage mediaand communication media. Computer storage media are tangible andmutually exclusive to communication media.

Computer storage media includes volatile and nonvolatile, removable andnon-removable media implemented in any method or technology, such assemiconductor, magnetic, or optical technologies, for storage ofinformation, such as computer-executable instructions, data structures,program modules or other data. Example computer storage media includes,but is not limited to, ROM 831, RAM 832, electrically erasableprogrammable read-only memory (EEPROM), solid-state memory, flashmemory, a hard disk, magnetic storage, floppy disk, magnetic tape, acompact disc (CD), a digital versatile disc (DVD), a BLU-RAY DISC® brandoptical disc, an ultra density optical (UDO) disc, or any other mediumwhich may be used to store the desired information and which may beaccessed by the computer 810. (BLU-RAY DISC® is a registered trademarkof Blu-ray Disc Association located in Burbank, Calif.). Computerstorage media are implemented in hardware and exclude carrier waves andpropagated signals. Computer storage media for purposes of thisdisclosure are not signals per se.

Communication media typically embodies computer-executable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism and includesany information delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media.

By way of example only, FIG. 8 illustrates a hard disk drive 841 thatreads from or writes to non-removable, nonvolatile magnetic media, auniversal serial bus (USB) port 842 that provides for reads from orwrites to a removable, nonvolatile memory 843, and an optical disk drive844 that reads from or writes to a removable, nonvolatile optical disk845. Other removable/non-removable, volatile/nonvolatile computerstorage media that may be used in the example operating environmentinclude, but are not limited to, solid state memory, flash memory, andthe like. The hard disk drive 841 may be connected to the system bus 830through a non-removable memory interface such as interface 846, andmagnetic disk drive 842 and optical disk drive 844 may be connected tothe system bus 830 by a removable memory interface, such as interface847.

The drives and their associated computer storage media, described aboveand illustrated in FIG. 8, provide storage of computer-executableinstructions, data structures, program modules, applications, components(e.g., interface component 510, account component 520, preauthorizationcomponent 530, identification component 540, detection component 550,dispenser component 560, modification component 570), and other data forthe computer 810. In FIG. 8, for example, hard disk drive 841 isillustrated as storing operating system 854, application programs 855,other program modules 856 and program data 857. Note that thesecomponents may either be the same as or different from operating system834, application programs 835, other program modules 836, and programdata 837. Operating system 854, application programs 855, other programmodules 856, and program data 857 are given different numbers herein toillustrate that, at a minimum, they are different copies.

The processing unit 820 includes any quantity of processing units, andthe instructions may be performed by the processing unit 820 or bymultiple processors within the operating environment 800 or performed bya processor external to the operating environment 800. The processingunit 820 may be programmed to execute the computer-executableinstructions for implementing aspects of the disclosure, such as thoseillustrated in the figures (e.g., FIGS. 4, 6, and 7). For example, theprocessing unit 820 may execute an interface component 510 (shown inFIG. 5), an account component 520 (shown in FIG. 5), a preauthorizationcomponent 530 (shown in FIG. 5), an identification component 540 (shownin FIG. 5), a detection component 550 (shown in FIG. 5), a dispensercomponent 560 (shown in FIG. 5), and/or a modification component 570(shown in FIG. 5) for implementing aspects of the disclosure.

Upon programming or execution of these components, the operatingenvironment 800 and/or processing unit 820 is transformed into a specialpurpose microprocessor or machine. For example, the preauthorizationcomponent 530, when executed by the processing unit 820, causes thecomputer 810 to obtain a preauthorization message associated with afinancial transaction, and analyze the preauthorization message toidentify a transaction amount and a cardholder account associated withthe financial transaction; the detection component 550, when executed bythe processing unit 820, causes the computer 810 to determine that acardholder associated with the cardholder account is proximate to a cashmachine, identify a capture time associated with the financialtransaction, and determine whether the capture time satisfies thetransaction timeframe; and the dispenser component 560, when executed bythe processing unit 820, causes the computer 810 to dispense thetransaction amount of cash in accordance with a nonvisual communicationprogram. Although the processing unit 820 is shown separate from thesystem memory 825, embodiments of the disclosure contemplate that thesystem memory 825 may be onboard the processing unit 820 such as in someembedded systems.

A user may enter commands and information into the computer 810 throughone or more input devices, such as a pointing device 861 (e.g., mouse,trackball, touch pad), a keyboard 862, a microphone 863, and/or anelectronic digitizer 864 (e.g., on a touchscreen). Other input devicesnot shown in FIG. 8 may include a joystick, a game pad, a controller, asatellite dish, a camera, a scanner, an accelerometer, or the like. Thecomputer 810 may accept input from the user in any way, including frominput devices, via gesture input, via proximity input (such as byhovering), and/or via voice input. These and other input devices may becoupled to the processing unit 820 through a user input interface 865that is coupled to the system bus 830, but may be connected by otherinterface and bus structures, such as a parallel port, game port or theUSB port 842.

Information, such as text, images, audio, video, graphics, alerts, andthe like, may be presented to a user via one or more presentationdevices, such as a monitor 866, a printer 867, and/or a speaker 868.Other presentation devices not shown in FIG. 8 may include a projector,a vibrating component, or the like. These and other presentation devicesmay be coupled to the processing unit 820 through a video interface 869(e.g., for a monitor 866 or a projector) and/or an output peripheralinterface 870 (e.g., for a printer 867, a speaker 868, and/or avibration component) that are coupled to the system bus 830, but may beconnected by other interface and bus structures, such as a parallelport, game port or the USB port 842. In some embodiments, thepresentation device is integrated with an input device configured toreceive information from the user (e.g., a capacitive touch-screenpanel, a controller including a vibrating component). Note that themonitor 866 and/or touch screen panel may be physically coupled to ahousing in which the computer 810 is incorporated, such as in atablet-type personal computer.

The computer 810 may operate in a networked environment using logicalconnections to one or more remote computers, such as a remote computer880. The remote computer 880 may be a personal computer, a server, arouter, a network PC, a peer device or other common network node, andtypically includes many or all of the elements described above relativeto the computer 810, although only a memory storage device 881 has beenillustrated in FIG. 8. The logical connections depicted in FIG. 8include one or more LANs 882 and one or more WANs 883, but may alsoinclude other networks. Such networking environments are commonplace inoffices, enterprise-wide computer networks, intranets and the Internet.

When used in a LAN networking environment, the computer 810 is coupledto the LAN 882 through a network interface or adapter 884. When used ina WAN networking environment, the computer 810 may include a modem 885or other means for establishing communications over the WAN 883, such asthe Internet. The modem 885, which may be internal or external, may beconnected to the system bus 830 via the user input interface 865 orother appropriate mechanism. A wireless networking component includingan interface and antenna may be coupled through a device, such as anaccess point or peer computer to a LAN 882 or WAN 883. In a networkedenvironment, program modules depicted relative to the computer 810, orportions thereof, may be stored in the remote memory storage device. Byway of example, and not limitation, FIG. 8 illustrates remoteapplication programs 886 as residing on memory storage device 881. Itmay be appreciated that the network connections shown are examples andother means of establishing a communications link between the computersmay be used.

The block diagram of FIG. 8 is merely illustrative of an example systemthat may be used in connection with one or more examples of thedisclosure and is not intended to be limiting in any way. Further,peripherals or components of the computing systems known in the art arenot shown, but are operable with aspects of the disclosure. At least aportion of the functionality of the various elements in FIG. 8 may beperformed by other elements in FIG. 8, or an entity (e.g., processor,web service, applications, server, computing system, etc.) not shown inFIG. 8.

Although described in connection with an example computing systemenvironment, embodiments of the disclosure are capable of implementationwith numerous other general purpose or special purpose computing systemenvironments, configurations, or devices. Embodiments of well-knowncomputing systems, environments, and/or configurations that may besuitable for use with aspects of the disclosure include, but are notlimited to, mobile devices, tablets laptop computers, desktop computers,server computers, microprocessor-based systems, multiprocessor systems,programmable consumer electronics, communication devices in wearable oraccessory form factors, portable media players, gaming consoles, set topboxes, kiosks, tabletop devices, industrial control devices,minicomputers, mainframe computers, network computers, distributedcomputing environments that include any of the above systems or devices,and the like.

Embodiments of the disclosure may be described in the general context ofcomputer-executable instructions, such as program modules, executed byone or more computers or other devices in software, firmware, hardware,or a combination thereof. The computer-executable instructions may beorganized into one or more computer-executable components or modules.Generally, program modules include, but are not limited to, routines,programs, objects, components, and data structures that performparticular tasks or implement particular abstract data types. Aspects ofthe disclosure may be implemented with any number and organization ofsuch components or modules. For example, aspects of the disclosure arenot limited to the specific computer-executable instructions or thespecific components or modules illustrated in the figures and describedherein. Other embodiments of the disclosure may include differentcomputer-executable instructions or components having more or lessfunctionality than illustrated and described herein.

In some embodiments, the operations illustrated in the drawings may beimplemented as software instructions encoded on a computer readablemedium, in hardware programmed or designed to perform the operations, orboth. For example, aspects of the disclosure may be implemented as asystem on a chip or other circuitry including a plurality ofinterconnected, electrically conductive elements.

The order of execution or performance of the operations in embodimentsof the disclosure illustrated and described herein is not essential,unless otherwise specified. That is, the operations may be performed inany order, unless otherwise specified, and embodiments of the disclosuremay include additional or fewer operations than those disclosed herein.For example, it is contemplated that executing or performing aparticular operation before, contemporaneously with, or after anotheroperation is within the scope of aspects of the disclosure.

The embodiments illustrated and described herein as well as embodimentsnot specifically described herein but within the scope of aspects of thedisclosure constitute example means for obtaining permission usingnonvisual communication to authorize one or more transactions. Forexample, the elements illustrated in FIGS. 1-3, 5, and 8, such as whenencoded to perform the operations illustrated in FIGS. 4, 6, and 7,constitute at least an example means for identifying a request forpreauthorization of a financial transaction (e.g., preauthorizationcomponent 530); an example means for determining a transaction timeframeassociated with a financial transaction (e.g., identification component540); an example means for identifying a cash machine associated with afinancial transaction (e.g., identification component 540); an examplemeans for determining whether to process a financial transaction inaccordance with a nonvisual communication program (e.g.,preauthorization component 530); and an example means for generating apreauthorization instruction to dispense the transaction amount of cashin accordance with a nonvisual communication program (e.g.,preauthorization component 530).

When introducing elements of aspects of the disclosure or theembodiments thereof, the articles “a,” “an,” “the,” and “said” areintended to mean that there are one or more of the elements.Furthermore, references to an “embodiment” or “example” of the presentdisclosure are not intended to be interpreted as excluding the existenceof additional embodiments or examples that also incorporate the recitedfeatures. The terms “comprising,” “including,” and “having” are intendedto be inclusive and mean that there may be additional elements otherthan the listed elements. The phrase “one or more of the following: A,B, and C” means “at least one of A and/or at least one of B and/or atleast one of C.”

Having described aspects of the disclosure in detail, it will beapparent that modifications and variations are possible withoutdeparting from the scope of aspects of the disclosure as defined in theappended claims. As various changes could be made in the aboveconstructions, products, and methods without departing from the scope ofaspects of the disclosure, it is intended that all matter contained inthe above description and shown in the accompanying drawings shall beinterpreted as illustrative and not in a limiting sense.

While the aspects of the disclosure have been described in terms ofvarious embodiments with their associated operations, a person skilledin the art would appreciate that a combination of operations from anynumber of different embodiments is also within the scope of the aspectsof the disclosure.

What is claimed is:
 1. A computing system for preauthorizing one or morefinancial transactions, the computing system comprising: a memory devicestoring data associated with one or more cardholder accounts andcomputer-executable instructions; and a processor configured to executethe computer-executable instructions to: receive, from a cashier system,a request for preauthorization of a first financial transaction of theone or more financial transactions, the request for preauthorizationincluding a transaction amount and a cardholder identifier; based on thecardholder identifier, identify a first cardholder account of the one ormore cardholder accounts; determine a transaction timeframe and one ormore machine identifiers associated with the first financialtransaction; access the first cardholder account to determine whether toprocess the first financial transaction in accordance with a nonvisualcommunication program; and on condition that the first financialtransaction is to be processed in accordance with the nonvisualcommunication program, generate an instruction to identify a capturetime associated with the first financial transaction, determine whetherthe capture time satisfies the transaction timeframe, and, on conditionthat the capture time satisfies the transaction timeframe, dispense thetransaction amount of cash in accordance with the nonvisualcommunication program.
 2. The computing system of claim 1, wherein theprocessor is further configured to execute the computer-executableinstructions to: transmit, to the cashier system, the instruction suchthat one or more cash machines are configured to dispense thetransaction amount of cash in accordance with the nonvisualcommunication program, the one or more cash machines associated with theone or more machine identifiers; and receive, from the cashier system, anotification indicative of the transaction amount of cash beingdispensed.
 3. The computing system of claim 1, wherein the processor isfurther configured to execute the computer-executable instructions to:identify user location data and time data associated with the firstfinancial transaction; and analyze the user location data and the timedata to identify one or more cash machines, the one or more cashmachines associated with the one or more machine identifiers.
 4. Thecomputing system of claim 1, wherein the processor is further configuredto execute the computer-executable instructions to: identify userlocation data and machine location data associated with the financialtransaction, the machine location data associated with the one or moremachine identifiers; and analyze the user location data and the machinelocation data to identify the transaction timeframe.
 5. The computingsystem of claim 1, wherein the processor is further configured toexecute the computer-executable instructions to: identify a plurality ofcash machines; generate a prompt to select, from the plurality of cashmachines, a set of cash machines; and receive user input associated witha selection of the set of cash machines, the selection of the set ofcash machines associated with the one or more machine identifiers. 6.The computing system of claim 1, wherein the processor is furtherconfigured to execute the computer-executable instructions to: receive adenomination breakdown corresponding to the transaction amount; andgenerate the instruction to dispense the transaction amount of cash inaccordance with the denomination breakdown.
 7. The computing system ofclaim 1, wherein the processor is further configured to execute thecomputer-executable instructions to: determine whether a hold durationassociated with the first financial transaction exceeds a holdthreshold; on condition that the hold duration exceeds the holdthreshold, transmit one or more of a request to modify the transactiontimeframe or a request to identify another cash machine.
 8. One or morecomputer storage media embodied with computer-executable instructions,the one or more computer storage media comprising: a preauthorizationcomponent that, upon execution by at least one processor, obtains apreauthorization message associated with a financial transaction, andanalyzes the preauthorization message to identify a transaction amountand a cardholder account associated with the financial transaction; adetection component that, upon execution by the at least one processor,determines that a cardholder associated with the cardholder account isproximate to a cash machine, identifies a capture time associated withthe financial transaction, and determines whether the capture timesatisfies the transaction timeframe; and a dispenser component that,upon execution by the at least one processor, dispenses the transactionamount of cash in accordance with a nonvisual communication program. 9.The one or more computer storage media of claim 8, wherein the detectioncomponent is configured to: obtain position data associated with one ormore of a user device associated with the cardholder account or anaccess card associated with the cardholder account; and analyze theposition data to determine whether the one or more of the user device orthe access card are proximate to the cash machine, the cardholderdetermined to be proximate to the cash machine on condition that the oneor more of the user device or the access card are proximate to the cashmachine.
 10. The one or more computer storage media of claim 8, whereinthe detection component is configured to: detect a transmissionassociated with one or more of a user device or an access card, the userdevice associated with a device identifier, the access card associatedwith a card identifier; and compare one or more of the device identifieror the card identifier with account data registered with the cardholderaccount to determine whether the one or more of the user device or theaccess card are associated with the cardholder account, the cardholderdetermined to be proximate to the cash machine on condition that the oneor more of the user device or the access card are associated with thecardholder account.
 11. The one or more computer storage media of claim8, wherein the detection component is configured to: detect an objectwithin a predetermined scan area; scan the predetermined scan area togenerate scan data; analyze the scan data to identify one or more of abiometric identifier associated with a user, a device identifierassociated with a user device, or a card identifier associated with anaccess card; and compare one or more of the biometric identifier, thedevice identifier, or the card identifier with account data registeredwith the cardholder account to determine whether the object isassociated with the cardholder account, the cardholder determined to beproximate to the cash machine on condition that the object is associatedwith the cardholder account.
 12. The one or more computer storage mediaof claim 8, wherein the dispenser account is configured to generate anotification indicative of the transaction amount of cash beingdispensed.
 13. The one or more computer storage media of claim 8,wherein the dispenser component is configured to: obtain a denominationbreakdown corresponding to the transaction amount; and dispense thetransaction amount of cash in accordance with the denominationbreakdown.
 14. The one or more computer storage media of claim 8 furthercomprising a modification component configured to: determine whether ahold duration associated with the financial transaction exceeds a holdthreshold; and on condition that the hold duration exceeds the holdthreshold, generate one or more of a request to modify the transactiontimeframe or a request to identify another cash machine.
 15. Acomputer-implemented method for preauthorizing one or more financialtransactions, the computer-implemented method comprising: identifying arequest for preauthorization of a first financial transaction of the oneor more financial transactions, the request for preauthorizationincluding a transaction amount and a cardholder identifier; determininga transaction timeframe associated with the first financial transaction;identifying one or more cash machines associated with the firstfinancial transaction; using the cardholder identifier to determinewhether to process the first financial transaction in accordance with anonvisual communication program; and on condition that the firstfinancial transaction is to be processed in accordance with thenonvisual communication program, generating a preauthorizationinstruction to dispense the transaction amount of cash in accordancewith the nonvisual communication program upon determining that a capturetime associated with the first financial transaction satisfies thetransaction timeframe.
 16. The computer-implemented method of claim 15,further comprising: identifying position data associated with ageolocation of a user device; identifying time data associated with anamount of time; and analyzing the position data and the time data toidentify the one or more cash machines.
 17. The computer-implementedmethod of claim 15, further comprising: identifying position dataassociated with a device location of a user device; identifying locationdata associated with one or more machine locations of the one or morecash machines; and analyzing the position data and the location data toidentify the transaction timeframe.
 18. The computer-implemented methodof claim 15, further comprising: identifying a plurality of cashmachines; prompting a user of the user device to select, from theplurality of cash machines, a set of cash machines; and receiving userinput associated with the selected set of cash machines, wherein the oneor more cash machines are identified based on the selected set of cashmachines.
 19. The computer-implemented method of claim 15, furthercomprising receiving a denomination breakdown corresponding to thetransaction amount, wherein the instruction is generated based on thedenomination breakdown.
 20. The computer-implemented method of claim 15,further comprising: determining whether a hold duration associated withthe first financial transaction exceeds a hold threshold; and oncondition that the hold duration exceeds the hold threshold,transmitting one or more of a request to modify the transactiontimeframe or a request to identify another cash machine.